-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Kotlin/Wasm doc updates for 2.3.0 release #5191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 2-3-0-doc-update
Are you sure you want to change the base?
Conversation
koshachy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to suggest some changes.
Feel free to contact me for details.
Cheers!
|
|
||
| Since Kotlin 2.0.0, we have introduced support for the new version of Wasm [exception handling proposal](https://github.com/WebAssembly/exception-handling/blob/main/proposals/exception-handling/Exceptions.md) within Kotlin/Wasm. | ||
| The [`wasmJs` target](wasm-overview.md#kotlin-wasm-and-compose-multiplatform) uses the legacy exception handling proposal by default. | ||
| The new proposal is turned off for this target, but |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The previous sentence already stated that the wasmJS uses the legacy exception handilng proposal.
Maybe we could rephrase the second part as
"To enable the new proposal for wasmJs target, use the ... compiler option."
| This update ensures the new exception handling proposal aligns with Kotlin requirements, enabling the use of Kotlin/Wasm on virtual machines that only support the latest version of the proposal. | ||
| The [`wasmWasi` target](wasm-overview.md#kotlin-wasm-and-wasi) uses the new proposal by default, | ||
| ensuring better compatibility with modern WebAssembly runtimes. | ||
| You can manually switch to the old proposal by |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To switch to the old (is it old or legacy? what is the right name?) proposal, use the ... compiler option"
| On Kotlin/Wasm targets, fully qualified names (FQNs) are available at runtime without any additional configuration. | ||
| This means that the `KClass.qualifiedName` property is enabled by default. | ||
|
|
||
| Having FQNs improves code portability from JVM to Wasm targets and makes runtime errors more informative by displaying |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to use more common verbs here:
Using FQNs improves code portability from JVM to Wasm targets and makes runtime errors more informative by showing the full qualified name.
WDYT?
|
|
||
| Currently, Kotlin/Wasm supports WASI 0.1, also known as Preview 1. | ||
| [Support for WASI 0.2 is planned for future releases](https://youtrack.jetbrains.com/issue/KT-64568). | ||
| [Support for WASI 0.2 is planned for future releases](https://youtrack.jetbrains.com/issue/KT-64568). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's explain better what behind the link. Smth like:
Follow this YouTrack issue for updates on WASI 0.2 support.
WDYT?
No description provided.